fix: render extension widgets next to the editor - #358
Merged
Conversation
jingxi1
pushed a commit
to jingxi1/pi-web
that referenced
this pull request
Aug 11, 2026
* fix: render extension widgets next to the editor * fix: cap extension widget lines --------- Co-authored-by: Alex Yang <agegcn@gmail.com> (cherry picked from commit 9e4ca65)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aboveEditorandbelowEditorrefer to the chat editor, but pi-web rendered those widgets in the scrollable message list. This moves them into the editor area, so they stay visible while the user reads a long conversation.aboveEditorwidgets render directly above the chat input.belowEditorwidgets render directly below the chat input.Testing
node_modules/.bin/tsc --noEmitnpm run lintScope
This changes widget placement only. It does not change the extension widget API or its server-side rendering and lifecycle behavior.